Virtual set-top box

ABSTRACT

A virtual set-top box (vSTB) for executing a middleware component, designed originally for use with the physical STB, including emulating hardware capabilities of the physical STB to process IPTV content received over a connection for presenting the IPTV content on a display of the electronic device.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 61/095,738, filed Sep. 10, 2008, which is hereby incorporated by reference. This application is related to co-pending U.S. Application No. not yet assigned, Attorney docket No. 8532P015, entitled “Dynamic Video Source Selection,” filed herewith.

FIELD OF THE INVENTION

This invention relates to Internet Protocol Television (IPTV) technology and, specifically, to a system and method for providing an IPTV service to a user such that the user may view programming content on a device such as a computer, the presentation and functionality associated with traditional programming paradigms being maintained.

BACKGROUND OF THE INVENTION

In the traditional television paradigm, programming content is sent as an analogue or digital signal to a viewer's television set via cable, satellite or through the air. The signals are then received, processed and displayed for the viewer to watch on the screen of the television set.

However, with the exoteric spread of portable electronic devices, such as laptop computers, viewers no longer wish to be restricted to watching television via a conventional television set which is, more or less, confined to use in one physical location. Given the desire or need for portability, and the ubiquitous presence of Internet-based technologies within modern computing equipment, the ability to receive IPTV services via computing equipment is becoming increasingly important from both a consumer's (i.e. viewer's) perspective and from the perspective of the service providers who seek to commercialize the opportunities.

Thus, the monopoly of the traditional television paradigm is being eroded and challenged by the development of Internet Television (Internet TV) and Internet Protocol Television (IPTV) technologies.

Internet TV enables a user to select programs from a list and is typically delivered over an IP network in the form of streaming video via a website. The content is embedded into a web page, and accompanying text is typically wrapped around the streaming video which is presented to the viewer within a separate window. In some ways, this presentation style is similar to a newspaper page wherein surrounding text flows around, not over the image, albeit that the static image is replaced by a video component.

By contrast, a typical IPTV system enables delivery of a digital television service to a viewer over a closed network infrastructure. The delivery is performed using Internet Protocol and typically includes a broadband connection. The IPTV system receives and displays the video stream, which has been encoded as a series of Internet Protocol (data) packets. IPTV can be in the form of live TV, but also as stored video —sometimes known as ‘video on demand’ (VOD).

Traditionally, the viewer must use a device known as a set-top box (STB) in conjunction with his/her television set in order to receive and view IPTV. The set top box acts as an interface between the television and the network, decoding the incoming video streaming media, converting it into standard television signals and providing two-way communications over the IP network. It also performs functional processing, such as setting up the connection and quality of service (QoS) with the service node, channel change functionality and user display control. This functionality is achieved via the use of software known as ‘middleware’.

‘Middleware’ is a key component within the IPTV solutions architecture. It is the application software layer that acts as an interface between the user interface and the hardware/operating system (OS) of the STB. Middleware vendors adopt abstraction based strategies to isolate themselves from the underlying hardware.

However, service providers can find it challenging to make the IPTV business model commercially viable due to the (often relatively high) cost of STBs. This is compounded by the linear nature of the cost/functionality line of STBs—the more features or functions the STB is required to posses, the higher the cost of the device. This has prompted IPTV service providers to investigate the possibilities of delivering their services to mass market end user devices (such as personal computers) where the cost of the hardware has already been borne by the end user/viewer. Thus, if standard computing components can be used to mirror and mimic their televisual counterparts (e.g. monitor, CPU, disk used to replace TV, STB, VCR respectively) then functionality can be maintained whilst eliminating the cost and inconvenience of a required STB.

In order to receive IPTV services and view them on other devices, such as a personal or laptop computer, there is a need, therefore, for the computer itself to perform the functional processing discussed above in relation to the STBs used with televisions.

Thus, there is a need for a system which provides the seamless delivery of IPTV services to an alternative device such as a computer. Ideally, such a system would be arranged and configured such that it can be integrated with existing IPTV technologies. This integration work is required, primarily, in 3 areas:

-   -   1) Video delivery: the solution must be based on standard         broadcast technologies, and not those which have emerged in         relation to web-based (Internet TV) services. This is because of         the difference in viewing experiences discussed above, primarily         in the segregation of text and moving images.     -   2) Conditional Access (CA): service providers require a means of         controlling and managing access to the services. Subscribers may         opt for varying levels of service, and thus access to the         content must be controlled via a conditional access system. This         is typically implemented via the use of virtual or traditional         hardware ‘smart cards’ used in conjunction with STBs. Ideally         such a system is managed from a single installation of the         customer's CA head-end and allows rights to be managed         seamlessly over heterogeneous display devices.     -   3) Middleware: middleware plays a key role in any IPTV system,         and determines the presentation layer of most services. The         choice of middleware is determined by the viewer's chosen         service provider and is typically of a client/server         architecture, the client residing on the STB. Typically,         middleware includes an application management component, an         execution environment, and the ability to access libraries         (Application Programming Interfaces—known as APIs) to control         the underlying hardware/OS.     -   Broadly speaking, known 3^(rd) party middleware can be         categorized into two types:         -   i) Category I middleware: middleware which is embedded             within the Document Object Model (DOM) of a STB's embedded             browser. These products use vendor-provided extensions to             that environment, in the form of ECMAScript libraries, to             control the media management elements of the service and             utilize standards based rendering technologies to render             their user interfaces—such as HTML & SVG;         -   ii) Category II middleware: middleware that is written             directly on top of the low-level APIs (typically implemented             in languages such as C or C++) provided by the STB vendors             to control the media management elements of the service and             typically utilize proprietary based rendering technologies             to render their user interfaces.

Both approaches suffer from the problem that the STB vendor provided APIs (both ECMAScript and C/C++) are not standardized and, therefore, each middleware vendor must perform a ‘porting’ exercise each time a new STB is to be added to their portfolio of supported end user devices.

Another problematic area facing would-be computer-based IPTV systems is that most known IPTV systems are designed to deliver IP encapsulated MPEG-2/4 content at 2 to 4 Mbps to users on multicast enabled networks. To date, the general lack of multicast support within large portions of the available networks restricts the number of potential target clients. There are several commercial and technical factors in existence, which remain barriers to the effective delivery of these services.

End users of television services are typically unconcerned with the underlying delivery mechanism employed to deliver the picture to their device (e.g. DTT, IP etc.). However, they are concerned about the quality of the content which they wish to view and the ease of use with which they access that optimal-quality content.

Therefore, a preferred solution should be capable of presenting a high quality service and consistent navigational paradigm to the viewer, whilst (behind the scenes) detecting, selecting and presenting the best quality programming possible based upon the current position of the viewer's device within the network (regardless of multicast support).

In other words, the solution should incorporate a dynamic video source selection (DVSS) mechanism, such that the user is provided with a single experience, of optimal quality on any network.

Known solutions attempt to address some of these difficulties, although they typically involve considerable expense from the service provider to effectively create a parallel distribution mechanism (encoding, encryption, delivery, middleware integration, device integration etc.), and typically provide a different viewing experience (in terms of presentation style and format, navigational interfaces etc.) from that which the viewer would expect from a traditional television based service.

In addition, many proposed solutions focus on how to deliver IPTV content to an end user, rather than how to process and/or display that content once it has been received at the client end, or how to improve/replace the technology employed at the client end.

For example, EP1895777 A1 discloses a method of providing an IPTV service to a subscriber, and a network element for executing said method. This is achieved by introducing an additional tier (an ‘intertwine’ tier) into the traditional 3 tiered IPTV architecture. This intertwine tier comprises IPTV service routers and a communication network, thus enabling provision of an IPTV service between different networks which may belong to different operators and/or be installed in different countries. Thus, the invention adds roaming functionality to the existing IPTV service.

However, the method and element disclosed in EP1895777 A1 do not enable a subscriber to receive and display ITPV content on an alternative device, such as a computer. Instead, the disclosed invention provides an alternative architecture for delivery of the programming content to the subscriber and does not address the issues discussed above concerning the technology employed at the client end.

Similarly, WO 2008/045384 A2 discloses an IPTV transport architecture with double layer encryption and bulk decryption. The disclosed invention is designed to operate in accordance with a client's traditional television/STB combination, and does not provide a means of presenting the programming content on an alternative device.

A number of systems are known in relation to STB simulation, for the purpose of testing constrained, isolated aspects of IPTV service delivery.

For example, the invention disclosed in EP 1914940 A1 provides a test apparatus for assessing the quality of an IPTV service, and to locate and repair malfunctions. The test apparatus accesses the IPTV network (from a central office) as a simulation of the user's STB, receives and analyses channel information and media contents downloaded from the IPTV network, and then generates test results. This obviates the need for an operator to enter the user's premises and perform the test routine using manual test apparatus. Thus, the STB simulation performed by the disclosed invention is limited such that it only simulates the way in which the STB presents itself to the network and receives information from the network. It does not present a fully operable STB emulation system which could be used to replace a user's STB and television and present the received content to the viewer. Thus, it does not provide a means of performing all the functions required and expected of a physical STB.

Similarly, US 2002/0026637 A1 discloses a computer program which allows a personal computer to emulate the functions of various STBs so that a combined video and an enhanced content stream can be displayed and randomly accessed to ensure that a desired layout is achieved with respect to the displayed content. The program is designed to facilitate quick and easy checking of the quality of the content presentation, with modification to the combined content stream being permitted during the checks if required. Thus, only one aspect of a traditional STB functionality is addressed by the disclosed invention, which does not provide a complete, alternative system for use in presenting IPTV content to an end user. The disclosed invention provides a means of pre-viewing video and interactive content by a producer rather than presenting a complete service to a user.

Neither US 2002/0026637 A1 nor EP 1914940 A1 address the problem of integrating different forms of existing middleware products with a STB emulation system. Neither do they include simulation components to support or emulate other traditionally required functions such as conditional access and other network management functions.

Thus it is an object of the invention to provide a means for receiving IPTV services on a user's device such as (but not exclusively) a personal computer, and presenting the IPTV content on the device, such that the viewer enjoys continuity of programming service regardless of his/her physical location or the underlying hardware/software platform of the device.

Thus, it is an object of the invention to provide a system and method for the simulation of a physical STB, and to enable standard computing components to mirror and mimic their televisual counterparts (e.g. monitor, CPU, disk→TV, STB, VCR).

It is an object of the invention to provide a solution which can be easily integrated with known IPTV technologies.

It is a further object of the invention to maintain substantially the same viewing experience as that experienced by a user when receiving and viewing televisual services via traditional (i.e. television plus physical STB) or alternative technologies. In other words, the content, navigational paradigm, presentation and quality of service must be substantially the same as those enjoyed by users of traditional IPTV systems.

It is a further object of the invention to provide a means of receiving and presenting said IPTV service such that 3^(rd) party category I or category II middleware, designed for execution by a physical STB, can execute in its usual manner and provide the same functionality on the viewer's computer without modification. The maintained functionality will typically include the ability to perform presentation layer rendering, video blending and multi-media control, and the provision of User Interfaces.

Thus, it is an object of the invention to provide a virtual STB application environment which not only emulates the underlying hardware capabilities of a physical STB (e.g. video scaling, video positioning, chroma keying, alpha blending, UI layout, Remote Control key handling etc.) but also provides the same software environment in terms of available APIs and libraries such that 3^(rd) party middleware is able to execute in this environment without modification.

It is a further object of the invention to provide a Conditional Access (CA) mechanism such that a service provider is able to control and manage the user's ability to access the programming content, said mechanism being easy to deliver and manage from a network/provider's perspective.

It is a further object of the invention to provide an IPTV system wherein the system is resource efficient (especially in respect of CPU usage and memory).

It is a further object of the invention to provide an IPTV system for receiving and presenting IPTV services on a user's device such that dynamic video source selection (DVSS) is achieved, wherein the system is able to determine and acquire the optimal quality programming possible based on the current position of the user's device within the network. It is preferred that this source selection is achieved dynamically, without the need for explicit input from the user.

Thus, the present invention provides a means of eliminating or alleviating at least one of the above identified problems, and achieving at least one of the above identified objectives.

SUMMARY OF THE INVENTION

In accordance with a first aspect of the present invention, there is provided a set-top box emulation system for presenting IPTV content to a user on an electronic device, said emulation system comprising:

-   -   i) a middleware component;     -   ii) a plurality of management components arranged and configured         to emulate the capabilities of a physical set-top box, wherein         the plurality of management components comprises at least one of         a presentation manager, a codec manager and/or a conditional         access manager; and     -   iii) a plurality of interfaces to enable communication between         said plurality of management components and said middleware,         wherein the plurality of interfaces comprises at least one of a         graphics interface, a MUX interface, a Conditional Access         interface, a Media interface, and Events Interface, a System         Settings interface and/or a Persistent Storage interface.

In a preferred embodiment of this first aspect, an IPTV system is arranged and configured such that a viewer can receive and watch IPTV televisual content displayed on an electronic device, said device acting as an alternative to a traditional television and STB combination. In a typical embodiment, said device is a personal or laptop computer, although other electronic devices may be used.

It is preferred that the televisual content is delivered from a service provider's head-end in the same way that it would be delivered to a STB being used in conjunction with a television set. When viewing said televisual content in accordance with the present invention, the navigational and presentation styles are maintained, and the format of the content is the same or substantially the same as that experienced by a viewer using a physical STB and television set.

Essentially, the invention provides a means for emulation of a traditional (physical) STB such that a virtual STB environment is created within the viewer's computer. The emulation is achieved by a software-based system which creates a virtual STB environment for other (known) software to interact with, such that the emulation system running on the computer presents itself to the network (and service provider) as if it were a physical STB connected to a television.

Preferably, the present invention has 3^(rd) party middleware embedded within it, said middleware being appropriate to the viewer's chosen service provider. That is to say, the virtual STB component acts as a wrapper around a vendor's middleware. Thus, a STB emulation component is installed on the end user's (i.e. viewer's) device, said emulation component encapsulating 3^(rd) party middleware which is appropriate for and compatible with the delivery system deployed by the user's chosen IPTV service provider.

Thus, in accordance with a first aspect of the invention, there is provided an API-based STB emulation environment within which known 3^(rd) party middleware (both category I and II) is able to execute. The execution and performance of the middleware is preserved in its traditional form, and the 3^(rd) party middleware interacts with the virtual STB environment (i.e. with the invention) as it would with a traditional STB operating within a traditional IPTV system. No modification of the vendor's middleware is required.

Thus, the viewer is able to view televisual content on an electronic device such as a personal or laptop computer, or other electronic device, by providing a virtual STB environment within the device, said virtual environment being able interface and interact with known 3^(rd) party middleware such that all aspects of functionality, performance and presentation formats are substantially identical to those enjoyed by users of a traditional IPTV (i.e. STB plus TV) configuration.

In accordance with a second aspect of the invention, the STB emulation component emulates the underlying hardware capabilities of a physical STB, thus enabling the same functionality (such as video scaling, video positioning, chroma keying, alpha blending, User Interface (UI) layout, Remote Control key handling and so on). These functions are emulated by a plurality of sub-components, each sub-component handling the emulation of a particular STB function. Each sub-component may, in turn, comprise one or more further sub components.

In a preferred embodiment of the first aspect of the invention, the sub-components of the STB emulation component may include (but are not restricted to) a player component, an embedded web browser, a management component, a decryption component and a set of one or more API libraries.

The STB emulation component may be configured, or tailored, to the viewer's (or service provider's) requirements via the use of configuration files, which store settings to enable and facilitate the management and control of the behavior of the STB emulation component.

In addition to the STB emulation environment, there is provided a set of core APIs which act as conduits into the 3^(rd) party middleware executing within the virtual (i.e. emulated STB) environment. These APIs are essential to the performance of the claimed invention.

The APIs service requests made by external applications and expose the functionality of the middleware to those applications. Thus, the STB emulation component operates in conjunction with the set of core APIs to enable the maintenance of connectivity between standard category I and II middleware and the IPTV service provider.

In other words, in order to facilitate management from the network operator perspective, there needs to be direct access into the embedded middleware by the service provider. If the middleware belongs to category I, this is achieved by DOM connectivity. If, however, the middleware belongs to category II then connectivity is achieved via the middleware's APIs which connect to the set of core APIs provided in accordance with the invention.

Thus, the emulated environment provided by the present invention is agnostic to 3^(rd) party middleware connectivity.

In a preferred embodiment of a first aspect of the invention, the APIs provide the following essential capabilities, although other interfaces may be included so as to extend the set of capabilities or, alternatively, some may not be required in alternative embodiments: a Graphics Interface, a MUX interface, a conditional Access (CA) Interface, a Media Interface, a Network Interface, an Event interface, a System Settings Interface and a Persistent Storage Interface.

In accordance with a second aspect of the invention, the middleware selected for use with the arrangement described above is category II (i.e. API-based) middleware. In a preferred embodiment, the user interface is handled by the category II middleware. The APIs provided in accordance with the present invention ‘plug into’ (i.e. provide connectivity with) the APIs provided within the 3^(rd) party category II middleware.

Thus, the category II middleware is able to operate within the emulated environment without any alteration or modification, even though it was designed originally for use with a physical STB (and television set) rather than a computer system.

In accordance with a third aspect of the invention, the arrangement described in relation to the first aspect is configured for use with category I (i.e. browser-based) middleware. In accordance with the third aspect of the invention, and in addition to the features listed in relation to the first aspect, there is provided a proprietary web browser. Preferably, the set of core interfaces described above (graphics interface, events interface etc.) integrate, or connect, with the proprietary browser. In a preferred embodiment, the user interface is handled by the proprietary browser, working in conjunction with the category I middleware.

In accordance with the third aspect of the invention, a set of STB emulation APIs (written in ECMAScript) is inserted into the DOM of the browser. Third party category I middleware is also inserted into the DOM of the browser. The STB emulation APIs emulate and/or replace the APIs which would traditionally be provided by the STB vendor. They take DOM requests and translate them into API requests.

Thus, the category I middleware is able to operate within the emulated environment without any alteration or modification, even though it was designed originally for use with a physical STB rather than a computer system.

For the sake of clarity, it should be noted that a typical embodiment of the emulation system described herein provides at least two sets of distinct APIs:

-   -   1) the set of APIs which are embedded within the proprietary         browser's DOM, providing genuine STB API emulation. These are         written in ECMAScript so as to enable their integration with the         embedded browser which forms a sub-component of the STB         emulation component; and     -   2) the set of APIs which are provided to enable the integration         of 3^(rd) party vendor middleware. These are written in a         language such as C or C++, and provide an extensible interface         between the 3^(rd) party category II middleware and the         underlying STB features. These are the fundamental links into         the middleware encapsulated or nested within the emulated         environment, and virtualize the core functions and hardware of         the traditional (physical) STB as listed above.

According to a fourth aspect of the invention, there is provided a Dynamic Video Source Selection (DVSS) component arranged and configured for use with the present invention.

As previously stated, viewers of IPTV programming content are not generally concerned with the underlying delivery mechanism(s) used to provide their viewing content. They do, however, care about the quality of that content, and the ease with which they can access their desired programs.

Thus, there is a need to provide, for the viewer, a consistent navigational paradigm whilst, behind the scenes, determining and acquiring the best quality programming available based upon the current position of the client device within the network. In summary, the aim of the DVSS component is to provide a consistent viewing experience, using any network, whilst maintaining optimal quality of service.

In addition, the provision of a DVSS component removes the need for a closed network, and allows the client device to receive ‘regular’ DVB based broadcast feeds (typically via a USB-based DVB-T dongle) and thus it is not mandatory that the video packets received via the network are encapsulated in IP. This approach is usually referred to as a ‘hybrid’ approach.

The functionality of the DVSS component can be decomposed into a number of key technical areas:

-   -   1) Dynamic network awareness: the client device needs to be         aware of the environment in which it finds itself. This implies         an ability to detect the capacity of a network to deliver         multicast traffic and, if so, at what bitrate. The bitrate         calculation should also take into account the possibility of two         (or more) devices which are attempting to source content over         the same DSL line.     -   2) Dynamic addressing and sourcing: This implies that the         metadata collected at the head-end should not multiply based on         the number of delivery mechanisms available to us. A simpler         approach would be to use a common identifier for the content and         then allow the client to determine the appropriate delivery         mechanism. For example, a channel asset is typically created for         Channell by associating it with a URL in the form of         IGMP://xxx.xxx.xxx.xxx:5000. This is unfortunate, as it strongly         implies that a multicast network is available (IGMP). However,         in accordance with a fourth aspect of the present invention, a         DVSS component provides the ability to issue the appropriate         requests independent of original URI based information—this         could, perhaps, be from multicast, USB based DVB-T devices or         other streaming technologies such as p2p or streamlets.     -   3) Network management: In order to deploy the present invention         to many residential viewers, it is essential that it is capable         of providing a network management feature that allows operators         the ability to manage it as if it were a network device such as         a STB or router. This is achieved by the implementation of a         TR-135 client that allows the invention to be managed by         standards-based TR-069 based management servers.

These and other aspects of the present invention will be apparent from and elucidated with reference to, the embodiment described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

An embodiment of the present invention will now be described, by way of example only, and with reference to the accompanying drawings, in which:

FIG. 1 shows a computer executing a 3^(rd) party middleware running in conjunction with the present invention, despite the middleware having been designed for use with a traditional STB;

FIG. 2 shows the primary components of a preferred embodiment of the present invention, in particular a typical arrangement wherein the APIs provide the essential interfaces between the operating systems and the emulated environment;

FIG. 3 shows an embodiment wherein the system is arranged and configured for use with (API-based) category II middleware;

FIG. 4 shows an embodiment wherein the system is arranged and configured for use with (browser embedded) category I middleware;

FIG. 5 shows how the televisual presentation of the service is preserved regardless of the device used to present the content;

FIG. 6 shows the reduction in effort and expense required on behalf of the service provider when using the present invention;

FIG. 7 shows the architecture of a typical, traditional IPTV system which utilizes a physical STB;

FIG. 8 shows how the architecture of traditional IPTV and web TV systems duplicate each other's core functions, and also shows the different presentation styles when content is displayed for viewing on the different end devices (i.e. a television plus physical STB displaying IPTV content versus a computer displaying web TV content);

FIG. 9 shows how the present invention eliminates or minimizes the duplication of core functions while providing content to either a television plus STB or computer being used in conjunction with the present invention, and also maintaining the presentation style of the content for the viewer;

FIG. 10 shows the main components in accordance with a preferred embodiment of the present invention, and illustrates its ability to treat the video and UI layers independently until the point of display on the end device;

FIG. 11 shows a detailed scheme of one aspect of the present invention, specifically the DVSS subsystem for performing dynamic source selection;

FIG. 12 shows the core components of a system arranged in accordance with an embodiment of the present invention to deliver IPTV content to a device for display to a viewer.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference to the above listed Figures, FIG. 7 shows how, in a traditional IPTV arrangement comprising a physical STB, content is delivered to a viewer's television set such that the presentation style of the content is the same as that experienced by the viewer when using a non-IPTV based delivery system. As FIG. 7 shows, signals are transmitted from the service provider over a network, and are forwarded by a router to the viewer's STB. The STB, which is connected to the viewer's television set, processes the signals such that the content can be displayed on the television screen in a style and format identical to that experienced in the more ‘traditional’ television broadcasting paradigms.

The present invention removes the need for a traditional (i.e. physical) STB or television set, and provides a software-based emulation environment such that the signals can be received, processed and viewed on an alternative device, such as a computer, without loss or adaptation of service, presentation style or functionality.

This maintenance of viewing experience is illustrated in FIG. 1 , which shows a laptop computer configured for use in accordance with the present invention, and illustrates how the invention has been architected to deliver a rich multi-media televisual experience akin to that traditionally associated with a physical STB and television set. The image shows the end result of how the 3^(rd) party middleware has elected to render the user interface and video layers with respect to each other.

Thus, the functional components of the invention (best illustrated in FIG. 10 ), coupled with the core APIs (shown in FIGS. 3 and 4 ) allow the middleware to define the exact co-ordinates of each visual element in all 3 planes (X, Y and Z). The Z-plane also includes the ability to apply alpha blending techniques to vary the opacity of the User Interface (UI) layer with respect to the video layer.

As shown in FIG. 6 , operators are typically forced to consider an almost complete duplication of their television infrastructure when they decide to target devices such as PCs with services. This is generally because the protocols and technologies associated with web TV delivery, as well as its navigational paradigms, differ from those of IPTV implementations. This is largely a result of technological limitations than choice.

When considering WebTV services, operators are usually forced to transrate or transcode their existing content into a more PC ‘friendly’ format such as Windows Media and Flash. This then requires the employment of alternative Conditional Access and Digital rights Management (DRM) strategies, and must finally re-design their whole UI/presentation layer to overcome the non-TV nature of their target device.

This leads, generally, to implementations where text flows around (not over) the video. FIGS. 7, 8 and 9 emphasize the point by illustrating the result of each of the architectures on the services that can be delivered to the end user.

According to a first aspect of the invention, a computing device is configured and arranged such that an operating system (OS) is able to execute on said computer, and is connected to a network such that data may be received from external source(s) over the network and/or sent to external source(s) over the network.

In addition, it is preferred that the computing device is arranged and configured to include a plurality of hardware components such as those included in a typical personal/laptop computing system. Such hardware components may include, but not be limited to:

-   -   i) a monitor (‘screen’) for displaying visual information and         programming content;     -   ii) speakers for presenting sounds and audio content; and     -   iii) a hard drive for recording programming content and/or other         data;

FIG. 2 shows how, according to a first aspect of the invention, a plurality of interfaces are provided to enable communication between the OS and the (category I or II) middleware which is embedded within the emulated environment. Said interfaces act as conduits for communication between the OS and components of the emulated STB environment. As such, the interfaces provide the fundamental links between the 3 party middleware embedded within the emulated environment.

FIG. 3 shows how the core interfaces (APIs) connect directly to the APIs provided by the category II middleware according to a second aspect of the invention. FIG. 4 shows how the core interfaces (APIs) connect to the proprietary web browser provided according to a third aspect of the invention, the category I middleware being embedded within the DOM of said browser and connecting to the browser via a STB API emulation component.

In a preferred embodiment, said interfaces may provide the following essential capabilities, although other interfaces may be included so as to extend the set of capabilities or, alternatively, some may not be required in alternative embodiments:

-   -   1) Graphics interface, providing the application within the         emulated STB environment with a mechanism to inform the         underlying graphical subsystem that something has changed and         that it should now refresh itself;     -   2) MUX interface, which enables the application within the         virtual STB environment to control the UI and video mixing         capabilities (including chroma keying and alpha blending);     -   3) CA interface, which enables applications to initiate the         registration of 3 party conditional access subsystems and to         interact with the features provided by those vendors;     -   4) Media interface, which enables applications executing within         the emulated STB environment to control the request, decode and         display of data streams. Said data streams could contain audio,         video or data information. This interface abstracts the         application from the underlying transport protocols and codecs         required to display the content and simplifies them into a         number of simple ‘play’ commands.         -   Fundamentally, this addresses the afore-mentioned need to             relieve the viewer of the burden of deciding which             underlying mechanism is required to receive the desired             televisual content. The viewer is not, typically, concerned             with selection between IGMP, RTSP, DVB-S/C/T or P2P. Thus,             the media interface services requests from the DVSS             component of the STB emulator, such that the viewer is able             to simply select the content (s)he wishes to watch, the             technical aspects of the optimal delivery mechanism being             handled ‘behind the scenes’. In other words, this subsystem             has the capability to make decisions based on the network             environment on how best to source and deliver the requested             content.

Preferably, this abstraction is continued with respect to both container formats and media types, being able to seamlessly decode multiple formats such as MPEG-1, MPEG-2, MPEG-4, WMV, Flash etc.

-   -   5) Network Interface, needed to support the abstracted network         delivery required by the Media Interface. This interface         provides modules for supporting standard video delivery         mechanisms: IGMP is provided to handle multicast IP based         broadcast content, an intelligent RTSP proxy is provided to         communicate in the appropriate RTSP dialect with RFC2326 based         servers. HTTP and HTTPS interfaces are also provided for         standard Web 2.0 based communications.     -   6) Event interface, which is the primary interface existing         between the OS based interface drivers for keyboard, mouse and         remote control devices to pass their inputs/actions on to the         application within the emulated STB environment.     -   7) System Settings Interface, which are provided (primarily) to         enable the operator to configure the virtual environment in         accordance with his needs and without having to make changes to         the STB emulation component itself.     -   8) Persistent Storage Interface, which provides a mechanism for         the application executing within the emulated environment to         store both content and content metadata on the local system to         enable such features as PVR and ‘off-line’ modes to be         implemented. Additionally, this may facilitate the operation of         some middleware products which require this feature to cache         carousel delivered EPG metadata.

Turning to FIG. 12 , a preferred embodiment of the invention is shown, and illustrates in greater detail the STB emulation component of the invention. Said emulation component comprises further subcomponents including:

-   -   i) A player component; it is preferred that the player component         comprises one or more sub-components, such as a hardware         abstraction layer, a video codec component, a DVB subtitle codec         component, a PID filter, and an audio codec component.     -   ii) API libraries; in a preferred embodiment, these are         implemented in a language such as Javascript, and may include a         display API (to provide connectivity with said player         component), an AV API (to provide connectivity with a DVSS         controller, which in turn integrates with said DVSS component)         and an Event API (which provides support for requests made by         the management component).     -   iii) An embedded web browser; it is preferred that the UI         functionality is performed via the embedded web browser provided         in accordance with the third aspect of the invention. The         embedded Javascript APIs enable the browser to integrate with         various other subcomponents of the emulator to control the user         interface. For example, a Display API is preferably provided so         as to handle requests made via the browser and requiring action         by a sub-component of the player component;     -   iv) A management component; this may further comprise         subcomponents such as a scheduler, a log/statistics maintenance         component, a license manager for handling the licensing of the         emulation component, a TR-135 client that allows the device to         be managed by standards based TR-069 management servers, and an         Event Listener which interacts with an Event API provided within         the Javascript API libraries.     -   v) A decryption component which integrates with said DVSS         component and said player component;

FIGS. 4 and 12 show a web browser embedded within a typical embodiment of the third aspect of the invention such that (when using category I middleware) UI functionality may be performed via the embedded proprietary browser. Preferably, the browser complies with the interfaces such that Category I middleware can be executed on the viewer's computer without modification. The STB API emulation component is inserted into the DOM of the browser (3) and accurately represents the interface corresponding to the STB which is being emulated. In a preferred embodiment, this API emulation component can be inserted dynamically and as such the browser is capable of emulating many standard IPTV STBs. The APIs themselves provide a mapping from the Javascript language directly to the underlying C APIs. The DOM object is also capable of registering callback events so that events occurring within the hardware environment can be reported back to the javascript application for auctioning.

Turning to a preferred embodiment of the fourth aspect of the invention, a DVSS component is provided and is integrated with the emulation sub-components described above. The DVSS component implements the concept of dynamic video source selection, which is most clearly illustrated in FIG. 11 .

Preferably, the DVSS component further comprises sub-components such as (but not restricted to) a PVR controller, an IGMP client, a RTSP client and a DVB-T client. The DVSS component integrates with a controller which in turn is supported by an AV API contained within the afore-said Javascript API libraries. In a preferred embodiment, the DVSS component may also integrate with the decryption component.

In a typical embodiment, a management component is provided which enables a network operator to manage the system as if it were a router or a physical STB. This further comprises a TR-135 client which allows the management according to standards based TR-069 based management servers.

In a typical embodiment, a decryption component is provided, and forms an interface between said DVSS component and said player component. The role of this component is to receive signals from a dynamically selected source, decrypt said signals and pass them on to the player component for further processing and display.

In a typical embodiment, API libraries, implemented in a language such as Javascript, are provided and may include a display API (to provide connectivity with said player component), an AV API (to provide connectivity with a DVSS controller, which in turn integrates with said DVSS component) and an Event API (which provides support for requests made by the management component).

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be capable of designing many alternative embodiments without departing from the scope of the invention as defined by the appended claims. In the claims, any reference signs placed in parentheses shall not be construed as limiting the claims. The word “comprising” and “comprises”, and the like, does not exclude the presence of elements or steps other than those listed in any claim or the specification as a whole. In the present specification, “comprises” means “includes or consists of” and “comprising” means “including or consisting of”. The singular reference of an element does not exclude the plural reference of such elements and vice-versa. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a device claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. 

1-20. (canceled)
 21. A method for streaming video media on an end user device, comprising: providing a plurality of management components to create a set-top box (STB) execution environment for a vendor application within the end user device, wherein: the vendor application is associated with a provider of streaming video media; and the plurality of management components comprises a conditional access (CA) component, a codec component, a decryption component, and a player component; providing, to the vendor application, a plurality of interfaces, wherein each interface is an interface to one of the plurality of management components; executing, by the end user device, the vendor application within the STB execution environment; managing access, via the CA component, to the streaming video media of the provider according to the vendor application via a CA interface of the plurality of interfaces; receiving a first streaming video media from the provider; decrypting, via the decryption component, the first streaming video media according to the vendor application via an encryption interface of the plurality of interfaces; decoding, via the codec component, the first streaming video media according to the vendor application via a codec interface of the plurality of interfaces; and presenting, by the end user device, the first streaming video media via the player component.
 22. The method of claim 21, wherein the vendor application is a middleware.
 23. The method of claim 21, wherein the vendor application is provided by the provider.
 24. The method of claim 21, wherein the STB execution environment supports a plurality of vendor applications.
 25. The method of claim 24, wherein the vendor application executed by the end user device is associated with the provider chosen by a viewer of the end user device.
 26. The method of claim 24, wherein each vendor application is associated with one of a plurality of providers of streaming video media, and wherein each vendor application is provided by its associated provider.
 27. The method of claim 21, wherein the vendor application executed by the end user device is associated with the provider chosen by a viewer of the end user device.
 28. An end user device comprising a processor and a non-transitory data storage comprising computer readable instructions that, when executed by the processor, perform an automated process for streaming video media, comprising: providing, to a vendor application stored within the end user device, a plurality of interfaces, wherein each interface is a programming interface to one of a plurality of management components of the end user device, and wherein: the plurality of management components creates a set-top box (STB) execution environment for the vendor application; the plurality of management components comprises a conditional access (CA) component, a codec component, a decryption component, and a player component; and the vendor application is associated with a provider of streaming video media; executing, by the end user device, the vendor application within the STB execution environment; managing access, via the CA component, to the streaming video media of the provider according to the vendor application via a CA interface of the plurality of interfaces; receiving, by the end user device, a first streaming video media from the provider; decrypting, via the decryption component, the first streaming video media according to the vendor application via an encryption interface of the plurality of interfaces; decoding, via the codec component, the first streaming video media according to the vendor application via a codec interface of the plurality of interfaces; and presenting, by the end user device, the first streaming video media via the player component.
 29. The end user device of claim 28, wherein the vendor application is a middleware.
 30. The end user device of claim 28, wherein the vendor application is provided by the provider.
 31. The end user device of claim 28, wherein the end user device supports a plurality of vendor applications.
 32. The end user device of claim 31, wherein the vendor application executed by the end user device is associated with the provider chosen by a viewer of the end user device.
 33. The end user device of claim 31, wherein each vendor application is associated with one of a plurality of providers of streaming video media, and wherein each vendor application is provided by its associated provider.
 34. The end user device of claim 28, wherein the vendor application executed by the end user device is associated with the provider chosen by a viewer of the end user device.
 35. An automated process to be performed by an end user device to stream video media, the automated process comprising: providing, by a set-top box (STB) execution environment operating on the end user device and to a vendor application stored within the end user device, a plurality of interfaces, wherein each interface is a programming interface to one of a plurality of management components of the end user device, and wherein: the plurality of management components comprises a conditional access (CA) component, a codec component, a decryption component, and a player component; and the vendor application is associated with a provider of streaming video media; executing, by the end user device, the vendor application; managing access, via the CA component, to the streaming video media of the provider according to the vendor application via a CA interface of the plurality of interfaces; receiving, by the end user device, a first streaming video media from the provider; decrypting, via the decryption component, the first streaming video media according to the vendor application via an encryption interface of the plurality of interfaces; decoding, via the codec component, the first streaming video media according to the vendor application via a codec interface of the plurality of interfaces; and presenting, by the end user device, the first streaming video media via the player component.
 36. The automated process of claim 35, wherein the vendor application is a middleware.
 37. The automated process of claim 35, wherein the vendor application is provided by the provider.
 38. The automated process of claim 35, wherein the end user device supports a plurality of vendor applications.
 39. The automated process of claim 38, wherein each vendor application is associated with one of a plurality of providers of streaming video media, and wherein the vendor application executed by the end user device is associated with the provider chosen by a viewer of the end user device.
 40. The automated process of claim 35, wherein the vendor application executed by the end user device is associated with the provider chosen by a viewer of the end user device. 